Use loggly's recommended MaxMessageSize of 64k #3074
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Use the suggested MaxMessageSize of 64kb:
Tests
After running
A run creator-node restart
,docker logs cn1_creator-node_1 --since 1s --follow
still worked as expected and the change was confirmed inrsyslog.conf
.How will this change be monitored? Are there sufficient logs?
We should now be able to import messages longer than 8k, which was the default.